home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20041116-20060924
/
000275_jaltman2@nyc.rr.com_Sun Mar 19 14:57:58 2006.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
4KB
Path: newsmaster.cc.columbia.edu!newsfeed.nyu.edu!News.Math.NCTU.edu.tw!newsfeed.news2me.com!nx01.iad01.newshosting.com!newshosting.com!207.115.63.142.MISMATCH!newscon02.news.prodigy.com!newscon06.news.prodigy.com!prodigy.net!news-east.rr.com!news-wrt-01.rdc-nyc.rr.com!news-feed-01.rdc-nyc.rr.com!news.rr.com!news-out.nyc.rr.com!news-wrt-01.rdc-nyc.rr.com.POSTED!53ab2750!not-for-mail
From: Jeffrey Altman <jaltman2@nyc.rr.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
Newsgroups: comp.protocols.kermit.misc
Subject: Re: closing a macro completely upon connect
References: <uGRPf.40748$VV4.591414@ursa-nb00s0.nbnet.nb.ca> <kLSPf.9392$X.1010@news-wrt-01.rdc-nyc.rr.com> <slrne10fck.8bc.fdc@sesame.cc.columbia.edu> <RqZPf.40942$VV4.594211@ursa-nb00s0.nbnet.nb.ca> <slrne10uul.jul.fdc@sesame.cc.columbia.edu> <H81Qf.41050$VV4.597519@ursa-nb00s0.nbnet.nb.ca> <ok2Qf.12766$nB6.1669@news-wrt-01.rdc-nyc.rr.com> <aQkQf.41491$VV4.608841@ursa-nb00s0.nbnet.nb.ca> <pVlQf.14280$4%1.10175@news-wrt-01.rdc-nyc.rr.com> <ATwQf.41716$VV4.616149@ursa-nb00s0.nbnet.nb.ca> <s3CQf.15925$nB6.6246@news-wrt-01.rdc-nyc.rr.com> <vmPQf.42198$VV4.628778@ursa-nb00s0.nbnet.nb.ca> <3CVQf.10658$X.5797@news-wrt-01.rdc-nyc.rr.com> <KaQRf.43750$VV4.667140@ursa-nb00s0.nbnet.nb.ca>
In-Reply-To: <KaQRf.43750$VV4.667140@ursa-nb00s0.nbnet.nb.ca>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Lines: 53
Message-ID: <EWZRf.18631$4%1.15@news-wrt-01.rdc-nyc.rr.com>
Date: Wed, 15 Mar 2006 19:29:40 GMT
NNTP-Posting-Host: 68.175.91.105
X-Complaints-To: abuse@rr.com
X-Trace: news-wrt-01.rdc-nyc.rr.com 1142450980 68.175.91.105 (Wed, 15 Mar 2006 14:29:40 EST)
NNTP-Posting-Date: Wed, 15 Mar 2006 14:29:40 EST
Organization: Road Runner High Speed Online http://www.rr.com
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:15528
The correct syntax for assigning macro "foo" to a key is
SET TERMINAL KEY <ttype> <keycode> \Kfoo
SET KEY <keycode> \Kfoo
If you don't specify the \K then you are assigning the string "foo" as
a string to be output to the host.
Please re-read what I have written. At no point have I indicated that
the ability to execute macros from keys when pressed in CONNECT mode is
going away. You have indicated a desire to have macros execute without
the switch from CONNECT mode to COMMAND mode. This is not going to occur.
Jeffrey Altman
Scott Caissie wrote:
> With the patch, can I still invoke a macro definition as a Kverb while in
> Connect mode?
>
> ie:
>> define doconnect {
>> CONNECT /SYNCHRONOUS
>> }
>
> for me to activate this while in Connect mode, I have to use: "Set key \???
> \kdoconnect".
> "Set key \??? doconnect" (not a kverb) just spams the word doconnect within
> the connect window while not activating the macro itself.
>
> Its the only way I know how to activate a macro from within the connect
> window.
> The ability to do this has amazing potential. I created a great deal amount
> of enhancements this way. If you like I can send a few to you.
> But apparently this is what.. an exploit? I had no reading materials when I
> first started researching this. Just the embedded help. After my 1st week of
> a great deal amount of trial and errors, this is what I came up with. I just
> kept figuring I was doing something wrong. Emailed Frank da Cruz about a way
> to activate macros from within the connect mode. On jan 14th, he said
> literarly: "There is a bug in the current version of Kermit 95 that prevents
> running macros from keystrokes".
>
> I always assumed that it was going to be corrected. I now have the book
> written by him. You're saying otherwise. Now my only concern is having all
> my work destroyed if this method is removed with the patch.
>
> All I need to know is if my work will continue to work with the patch. Right
> now I don't know if I want patch anymore. I'm afraid that it'll ruin
> everything. We're rather dependant on those enhancements now. I scrapped
> that one macro until later on. Everything else is at 100% and I wish to keep
> it that way.
>
>